====================================================================
Upgrading from Repertoire 7/8.x to >=8.7.1
====================================================================

* Java 7 or greater is required

====================================================================
Upgrading from Repertoire 7 to 8
====================================================================

* Java version 1.6 or greater is required

====================================================================
Upgrading from Repertoire 7.1 or earlier
====================================================================

* Re-install Windows Service

Minor changes in the startup script are required when upgrading from
version 7.1 or earlier. The following two Java system options are 
not needed anymore: 

-Djava.security.auth.login.config and -Djava.security.policy.

If you are launching Repertoire server as a Windows service, you need
to update (uninstall and install) the Windows service using the tools
provided under 'windows-service' directory.

* Javascript security has been enhanced

We have enhanced security support for Javascript so that scripts
written by users will be executed with limited privileges (these are
configurable by administrators).

If you have a script that ran correctly with version 7.1 or earlier, 
but fails in the new release, you should check if the script contains 
privileged actions (such as establishing network connections or 
accessing files on hard disk, etc.). You should verify that these 
operations are safe and if you believe they are necessary, you can 
then fine tune the security policies in config\java2.policy for your 
users. Please see the user manual for more details.

====================================================================
Upgrading from Repertoire 6 to 7
====================================================================

Migration effort from Repertoire 6 to Repertoire 7 should be minimal. 
Reports, Data Sources, Dashboards are kept compatible.  However, it 
is advisable to set up a test environment to ensure that your 
application is working fine with Repertoire 7.  

Repertoire 7 requires Java runtime version 1.5.0_08 or later.

Repertoire Server 7 has greatly improved the configurability of the 
system environment such as repository filesystem and user access 
security. A web interface is provided for administration, 
repository browsing, triggering of reports, and accessing to 
reports, data sources and dashboards.  

The JMX HTTP console is no longer required as system monitoring is 
supported via standard Java JMX console, available as part of Java 
Development Kit.

Repertoire Server 7 provides a new REST APIs to access the entire 
range of server services. The Java ERSClient API for rendering 
reports and data sources is retained for backward compatibility.

Perspective is now part of Repertoire 7 Server component.  
The Perspective Servlet web archive file or a separate J2EE server 
is no longer required. You are advised to retest all dashboards 
designed in Repertoire 6 with Repertoire 7 Designer and Server.  
Minor modifications may be needed to support new features implemented 
such as a fixed-sized card dimension and the use of borders with 
margin and padding for aesthetic and precision layout control.

Checklist

General 

* Java Runtime Environment (JRE) version 1.5.0_08 or later.

* Repertoire 7 license keys.

Server

* Administration Web interface provided for configuring
  - Group and user/password setting
  - Default administrator account for server login is 
    user = admin and password = sa.
  - Repository setup and access control
  
* A web interface for navigating the filesystems to view and 
  render reports, dashboards, data sources and jobs.  
  The HTML and CSS files for this interface can be customized 
  with any web editing tools.
  
* There is no more JMX HTTP client and port 8089 is no longer used. 
  To use JMX, please refer to JMX console configuration for your 
  specific Java version.
  
* Web browser required are Mozilla Firefox version 2 and Microsoft 
  Internet Explorer version 6 or later.  However, as IE6 has bug in 
  transparency support, one should use IE7 for dashboard rendering 
  in particular where transparency is used extensively.
  
* Default port configuration 
  - 8080 for Remote and web view  (configurable)
  or
  - 8443 for HTTPS secure connection (configurable)
  
* Remote Designer requires Java Web Start to be available, which is 
  now part of newer Java Runtime Environment installation like in Java SE 6.

Server Configuration 

* Server configuration in ERS2.xml
  - Default Port number is 8080 

* Secured connection 
  - HTTPS configuration (Please refer to Elixir Repertoire Server 
   User Manual included in the software package)

* Target
  - ReplyTarget is implicit. No need to set the target as me.

* Repository 
  - Setting is no more in a file but is kept in a built-in database 
    which can only be accessed via web-based administration.

* User and Group 
  - Role in Repertoire 6 Server is replaced by Group in Repertoire 7 Server.
  - Configuration can only be made via web-based administration.

* Part of configuration is stored in a database, Apache Derby. 
  The RepertoireServer\db data can be archived and import into 
  a new server instance. 

* Various logs are accessible via web-based administration. 

Client 

* Updated RepertoireClient.jar for Repertoire 7 Server.

* JDom is not longer needed. 

* Internally, the client uses the REST API over HTTP protocol.

====================================================================
Upgrading from Repertoire 1.5.0 or earlier:
====================================================================

In Repertoire version 1.5.0 and earlier, HBox and VBox components 
sometimes did not correctly update the position of child components
when they were moved or resized. This issue was fixed in version 1.5.1. 

Please note that some components inside HBox and VBox might therefore 
appear in a slightly different location compared with older versions that 
exhibited this bug. The new location is the correct one as the constraints
of the HBox and VBox are now properly enforced.
